Troubleshooting custom profile configurations

Some custom profile configurations can cause errors when being applied to target devices. This can happen due to several reasons, some of which are listed below. You can review the errors in the Device History, and also in the Windows Event Viewer on target devices, under Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin. The following examples illustrate the cause of such errors and how they are reported:

• CSP (configuration service providers) not supported on the target Windows version:
  • KACE Cloud Device History: Error: 500: Command failed. 507: Atomic failed.
  • Windows Event Viewer: MDM ConfigurationManager: Command failure status. Configuration Source ID: (C89EE653-52C7-422A-8AD0-06B786634FF0), Enrollment Name: (MDMFull), Provider Name: (Policy), Command Type: (Add: from Replace or Add), CSP URI: (./User/Vendor/MSFT/Policy/Config/Start/DisableControlCenter), Result: (The system cannot find the file specified.).

  This error can be caused by a policy that is not supported on the OS version of the target device. For example, DisableControlCenter is only valid in Windows 11 22H2, and attempting to apply it to a device with a lower OS version causes the above error.

• Wrong data type:
  • KACE Cloud Device History: Error: 415: Unsupported media type or format. 507: Atomic failed.
  • Windows Event Viewer: No error message.
• CSP not valid (bad syntax):
  • KACE Cloud Device History: Error: 404: Not found. 507: Atomic failed.
  • Windows Event Viewer: No error message.

  This error can be caused by a wrong OMA-URI path. For example, the OMA-URI path specified in the custom profile is ./Device/Vendor/MSFT/Start/HideSleep (invalid) instead of /Device/Vendor/MSFT/Policy/Config/Start/HideSleep (valid).